-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement PIN protocol 2 and PIN token permissions #63
Conversation
This patch removes the assumption that we only support PIN protocol 1 from the CTAP2 implementation. Instead, a list of supported PIN protocols is provided by the pin_protocols function and parse_pin_protocol can be used to validate the PIN protocol selected by the platform. The parsed PIN protocol version must then be passed to the pin_protcol function to access the correct implementation.
462e305
to
c53bbea
Compare
Updated to include PIN token permissions so that testing is feasible. This branch should include a working firmware version with these changes: https://github.com/Nitrokey/nitrokey-3-firmware/tree/fido-pin-protocol-2 |
A potential point for discussion is naming. What used to be the pinToken in CTAP 2.0 is now the pinUvAuthToken. For simplicity, I just kept the |
naming: I think testing https://github.com/Nitrokey/nitrokey-3-firmware/tree/fido-pin-protocol-2 for regressions and functionality against pynitrokey (master) with Nitrokey/pynitrokey#507 included:
soooo, lgtm! |
c53bbea
to
fea9eb4
Compare
fea9eb4
to
87e3aef
Compare
Based on: